home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The CICA Windows Explosion!
/
The CICA Windows Explosion! - Disc 2.iso
/
nt
/
ntkb.zip
/
NTKB.EXE
/
Q103
/
8
/
65.TXT
< prev
next >
Wrap
Text File
|
1993-10-07
|
4KB
|
111 lines
DOCUMENT:Q103865 06-OCT-1993 [W_NT]
TITLE :Load And Run Values with Third-Party Shell Programs
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:
--------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server version 3.1
--------------------------------------------------------------------------
WARNING: Using Registry Editor incorrectly can cause serious, system-wide
problems that may require you to reinstall Windows NT to correct
them. Microsoft cannot guarantee that any problems resulting from
the use of Registry Editor can be solved. Use this tool at your
own risk.
SUMMARY
=======
When a shell other than Program Manager (PROGMAN.EXE) is being used,
the run and load entries in the registry might be ignored.
MORE INFORMATION
================
A common way to run or load applications at startup in Windows 3.x is
to add the filename to the load= or run= line in the WIN.INI file.
Windows NT translates these entries to the following registry key and
values:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
load: REG_SZ
run: REG_SZ
They operate exactly the same as in Windows 3.0 and 3.1 as long as
Program Manager is used as the shell; however, if a replacement for
Program Manager is specified in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT
\CurrentVersion\Winlogon - Shell
any programs set to load automatically (through the load value, run
value, or the Startup group) when Windows NT is started, it will not
load unless the third-party shell is written to search for such
values.
Steps to Reproduce Problem
--------------------------
1. Start Registry Editor, REGEDT32.EXE.
2. Select HKEY_CURRENT_USER\Software\Microsoft\Windows NT
\CurrentVersion\Windows.
3. In the Value window, double-click Load to open String Editor.
4. Type the following and then press ENTER:
clock
Choose OK.
5. Quit Registry Editor and log off from Windows NT.
6. Log on as the same user and notice that Clock appears in the
lower-left corner.
7. Start Registry Editor again.
8 Select HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\
CurrentVersion\Winlogon.
9. In the Value window, double-click Shell to open String Editor.
10. Type the following and then press ENTER:
winfile,taskman,wowexec
Choose OK.
11. Quit Registry Editor and log off from Windows NT.
Logon as the same user and notice that File Manager comes up as the
shell, but Clock does not appear.
To return the system to its previous state, repeat steps 1-4 and 8-11,
removing "clock" on step 4 and entering "progman,wowexec" in step 10.
Additional reference words: 3.10 third party 3rdparty
KBCategory:
KBSubCategory: 16ap 32ap winnt
=============================================================================
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1993.